Skip to content

Release v0.20.0#1334

Merged
kovtcharov-amd merged 7 commits into
mainfrom
v0.20.0-release
Jun 3, 2026
Merged

Release v0.20.0#1334
kovtcharov-amd merged 7 commits into
mainfrom
v0.20.0-release

Conversation

@kovtcharov-amd
Copy link
Copy Markdown
Collaborator

@kovtcharov-amd kovtcharov-amd commented Jun 1, 2026

Cuts the v0.20.0 release. Headline changes: per-agent device selection (CPU / GPU / Ryzen AI NPU), per-agent MCP tool-visibility activations with live SSE updates, a terminal-native Agent Hub (gaia with no args), ~10× faster bulk email organization, native PowerPoint indexing for RAG, and a broad security / first-boot / test-infrastructure hardening pass.

Full, commit-by-commit notes live in docs/releases/v0.20.0.mdx — that file is the source of truth and is kept in sync with the v0.19.0..HEAD range.

Release checklist

  • util/validate_release_notes.py docs/releases/v0.20.0.mdx --tag v0.20.0 passes
  • src/gaia/version.py0.20.0
  • src/gaia/apps/webui/package.json0.20.0
  • Navbar label in docs/docs.jsonv0.20.0 · Lemonade 10.2.0
  • All commits in range (v0.19.0..HEAD) represented in the notes
  • Review from @kovtcharov-amd addressed

@github-actions github-actions Bot added the documentation Documentation changes label Jun 1, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

Summary

This is a clean, well-executed release documentation PR that correctly bumps the version to 0.20.0 across all three required locations and ships accurate, value-prop-first release notes covering all 44 commits in the range. The notes follow GAIA's "lead with impact, not implementation" style consistently and the navigation wiring in docs/docs.json is correct.

Issues Found

🟢 Minor — One changelog entry lacks conventional-commits prefix (docs/releases/v0.20.0.mdx:154)

The Full Changelog entry for PR #1221 reads:

d05ddc52 — Skip unreadable agent dirs during export (#1221)

Every other entry follows type(scope): description format. This is the original commit message (this PR can't change it), so flagging it only for awareness — future commits should follow the convention.


🟢 Minor — Frontmatter description is 233 characters (docs/releases/v0.20.0.mdx:2)

Mintlify uses this field for SEO meta-description; most search engines truncate at ~160 characters. The v0.19.0 notes have a similarly long description (255 chars), so this is a project-wide pattern rather than an error. Trimming to ≤160 chars would improve SEO, but it's not blocking.

description: "Per-agent CPU/GPU/NPU selection, MCP tool-visibility activations, Agent Hub TUI, 10x faster email batch tools, native .pptx RAG, and a broad security and test-infrastructure hardening pass."

Strengths

  • Version consistencysrc/gaia/version.py, src/gaia/apps/webui/package.json, and the docs/docs.json navbar label are all bumped together; no drift between the three locations.
  • Accurate changelog coverage — the Full Changelog section accounts for all 44 commits in the v0.19.0..v0.20.0 range, including the two installers fixes (fix(installer): resolve repo root correctly in scripts under installer/ #1326, fix(installer): resolve repo root correctly in bash scripts under installer/ #1332) that landed late in the cycle.
  • Release notes prose quality — each section leads with the user-observable before/after state ("previously told users to save it as PDF first", "sent first-boot into a destructive delete + ~25 GB re-download"), with PR and issue links for every change, no Claude attribution anywhere, and no padded "what changed" enumeration.

Verdict

Approve. No blocking issues. The single actionable suggestion (trimming the frontmatter description) is optional. The PR is ready to merge.

itomek-amd
itomek-amd previously approved these changes Jun 1, 2026
Ovtcharov added 2 commits June 2, 2026 22:22
19 PRs merged to main after the v0.20.0 notes were drafted; merge main into
the release branch and update the notes to match.

- Multi-Device: note #1338 wired the selector end-to-end (it was a no-op
  after #1252 alone) and added loud runtime validation for unavailable devices.
- PowerPoint RAG: note #1366 unblocked .pptx in the Agent UI file picker
  (backend already accepted it; the frontend rejected it pre-upload).
- Activations: note #1310 widened the "Active for" panel to MCP-consuming
  agents (e.g. the chat agent), not just static REQUIRED_CONNECTORS.
- New bug fixes: RAG embedding reuse (#1306), overlapping-chat-turn 409
  (#1304), Memory/Settings mutual exclusivity (#1368).
- Tooling/CI: doc-vs-code realignment (#1298/#1337/#1340), gaia-testing
  skill (#1372), Claude CI + Codecov hardening.
- Full Changelog regenerated: 44 -> 63 commits.
itomek-amd
itomek-amd previously approved these changes Jun 3, 2026
@kovtcharov-amd kovtcharov-amd enabled auto-merge June 3, 2026 18:37
@kovtcharov-amd kovtcharov-amd added this pull request to the merge queue Jun 3, 2026
Merged via the queue into main with commit deaee39 Jun 3, 2026
49 checks passed
@kovtcharov-amd kovtcharov-amd deleted the v0.20.0-release branch June 3, 2026 18:38
pull Bot pushed a commit to bhardwajRahul/gaia that referenced this pull request Jun 3, 2026
…p 429 flakes (amd#1379)

The Linux "Full Integration" CI job has been flaking on every release/PR
— including the v0.20.0 release PR (amd#1334) and amd#1377. Root cause: it
pulls `Qwen3-0.6B-GGUF` from HuggingFace **unauthenticated**, so shared
GitHub runners hit `429 Too Many Requests`, Lemonade fails to start, and
the whole job (summarizer/RAG/lemonade-client integration) fails. The
Windows CLI, SD, and Agent SDK jobs already pass `HF_TOKEN` and never
flake — this just brings the Linux job to parity.

After this, the Linux integration job authenticates its model pulls and
stops 429-flaking.

## Test plan
- [ ] CI on this PR: **GAIA CLI Tests (Linux) → Test GAIA CLI on Linux
(Full Integration)** reaches the model pull without a `429` and passes
- [ ] Confirm no secret leakage in logs (GitHub masks `secrets.*`
automatically)

Co-authored-by: Ovtcharov <kovtchar@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants